v3.3.0

Compare Source

Features

• Add types to package (#​179) (cb546be)

v9.22.0

Compare Source

v9.21.0

Compare Source

Features

• 418717f feat: introduce new deprecated types for rules (#​19238) (fnx)
• 5c5b802 feat: Add --ext CLI option (#​19405) (Milos Djermanovic)

Bug Fixes

• db5340d fix: update missing plugin message template (#​19445) (Milos Djermanovic)
• d8ffdd4 fix: do not exit process on rule crash (#​19436) (Francesco Trotta)

Documentation

• c5561ea docs: Update README (GitHub Actions Bot)
• 80b0485 docs: replace var with let and const in rule example (#​19434) (Tanuj Kanti)
• f67d5e8 docs: Update README (GitHub Actions Bot)
• 75afc61 docs: Update README (GitHub Actions Bot)
• 0636cab docs: Update Eleventy from v2 to v3 (#​19415) (Amaresh S M)
• dd7d930 docs: Update README (GitHub Actions Bot)

Chores

• a8c9a9f chore: update @eslint/eslintrc and @eslint/js (#​19453) (Francesco Trotta)
• 265e0cf chore: package.json update for @​eslint/js release (Jenkins)
• 3401b85 test: add test for Rule.ReportDescriptor type (#​19449) (Francesco Trotta)
• e497aa7 chore: update rewrite dependencies (#​19448) (Francesco Trotta)
• dab5478 chore: better error message for missing plugin in config (#​19402) (Tanuj Kanti)
• ebfe2eb chore: set js language for bug report issue config block (#​19439) (Josh Goldberg ✨)
• 5fd211d test: processors can return subpaths (#​19425) (Milos Djermanovic)

v9.20.0

Compare Source

Features

• e89a54a feat: change behavior of inactive flags (#​19386) (Milos Djermanovic)

Bug Fixes

• 91d4d9f fix: Bring types in sync with @​eslint/core (#​19157) (Nicholas C. Zakas)
• fa25c7a fix: Emit warning when empty config file is used (#​19399) (Nicholas C. Zakas)
• 31a9fd0 fix: Clearer error message for wrong plugin format (#​19380) (Nicholas C. Zakas)
• 61d99e3 fix: Better error message for unserializable parser (#​19384) (Nicholas C. Zakas)
• db1b9a6 fix: Ensure module scope is checked for references in consistent-this (#​19383) (Nicholas C. Zakas)
• 8bcd820 fix: arrow-body-style crash with single-token body (#​19379) (Milos Djermanovic)

Documentation

• b7012c8 docs: rewrite examples with var using let and const (#​19407) (Mueez Javaid Hashmi)
• 6406376 docs: Update README (GitHub Actions Bot)
• 350f2b9 docs: rewrite some examples with var using let and const (#​19404) (Mueez Javaid Hashmi)
• 93c325a docs: rewrite examples with var using let and const (#​19398) (Mueez Javaid Hashmi)
• 56ff404 docs: replace var with let or const in rules docs (#​19396) (Daniel Harbrueger)
• 4053226 docs: change sourceType in no-eval examples (#​19393) (Milos Djermanovic)
• 1324af0 docs: replace var with let and const in rules docs (#​19392) (Daniel Harbrueger)
• 8b87e00 docs: replace var with const and let in rules (#​19389) (Tanuj Kanti)
• 758c66b docs: Explain what frozen rules mean (#​19382) (Nicholas C. Zakas)
• 0ef8bb8 docs: additional checks for rule examples (#​19358) (Milos Djermanovic)
• 58ab2f6 docs: fix order of installation steps in getting started (#​19326) (Tanuj Kanti)

Chores

• 979097a chore: upgrade @​eslint/js@​9.20.0 (#​19412) (Francesco Trotta)
• 031734e chore: package.json update for @​eslint/js release (Jenkins)
• d4c47c3 test: avoid empty config warning in test output (#​19408) (Milos Djermanovic)
• 67dd82a chore: update dependency @​eslint/json to ^0.10.0 (#​19387) (renovate[bot])
• 15ac0e1 chore: add permissions: read-all to stale.yml workflow (#​19374) (Josh Goldberg ✨)

v8.26.1

Compare Source

🩹 Fixes

• eslint-plugin: [no-unsafe-return] handle recursive type (#​10883)
• eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as eligible for nullish coalescing (#​10865)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

v8.26.0

Compare Source

🚀 Features

• eslint-plugin: [unified-signatures] support ignoring overload signatures with different JSDoc comments (#​10781)
• eslint-plugin: [explicit-module-boundary-types] add an option to ignore overload implementations (#​10889)
• eslint-plugin: [no-unused-var] handle implicit exports in declaration files (#​10714)
• support TypeScript 5.8 (#​10903)
• eslint-plugin: [no-unnecessary-type-parameters] special case tuples and parameter location arrays as single-use (#​9536)

🩹 Fixes

• eslint-plugin: [no-unnecessary-type-assertion] handle unknown (#​10875)
• eslint-plugin: [no-invalid-void-type] report accessor properties with an invalid void type (#​10864)
• eslint-plugin: [unified-signatures] does not differentiate truly private methods (#​10806)

❤️ Thank You

• Andrea Simone Costa @​jfet97
• Dirk Luijk @​dirkluijk
• Ronen Amiel
• YeonJuan @​yeonjuan
• Yukihiro Hasegawa @​y-hsgw

You can read about our versioning strategy and releases on our website.

v8.25.0

Compare Source

🚀 Features

• eslint-plugin: [no-misused-spread] add suggestions (#​10719)

🩹 Fixes

• eslint-plugin: [prefer-nullish-coalescing] report on chain expressions in a ternary (#​10708)
• eslint-plugin: [no-deprecated] report usage of deprecated private identifiers (#​10844)
• eslint-plugin: [unified-signatures] handle getter-setter (#​10818)

❤️ Thank You

• Olivier Zalmanski @​OlivierZal
• Ronen Amiel
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

v8.24.1

Compare Source

🩹 Fixes

• eslint-plugin: [class-methods-use-this] check accessor methods with a function initializer (#​10796)
• eslint-plugin: [no-misused-promises] don't report on static accessor properties (#​10814)
• eslint-plugin: [no-deprecated] don't report on deprecated accessor property declaration (#​10813)
• eslint-plugin: [explicit-member-accessibility] check accessor class properties for missing accessibility modifier (#​10805)
• eslint-plugin: [explicit-module-boundary-types] check accessor class properties with a function initializer (#​10804)
• eslint-plugin: [prefer-return-this-type] check accessor properties with a function initializer (#​10794)
• eslint-plugin: [consistent-generic-constructors] check accessor class properties (#​10789)
• eslint-plugin: [no-unsafe-assignment] report on an any value assigned as an initializer of an accessor property (#​10785)
• eslint-plugin: [no-unnecessary-template-expression] ignore enum and enum members (#​10782)
• eslint-plugin: [no-inferrable-types] handle accessor (#​10780)

❤️ Thank You

• Ronen Amiel
• YeonJuan

You can read about our versioning strategy and releases on our website.

v8.24.0

Compare Source

🚀 Features

• eslint-plugin: [no-unnecessary-condition] make allowConstantLoopConditions more granular (#​10639)

🩹 Fixes

• eslint-plugin: [no-misused-spread] correct and elaborate string spread report message (#​10751)
• eslint-plugin: [restrict-plus-operands] report adding bigints to strings when allowNumberAndString is false (#​10737)

❤️ Thank You

• Josh Goldberg ✨
• noah
• Ronen Amiel

You can read about our versioning strategy and releases on our website.

v8.23.0

Compare Source

🚀 Features

• eslint-plugin: [no-unnecessary-boolean-literal-compare] enforce strictNullChecks (#​10712)

🩹 Fixes

• eslint-plugin: [no-shadow] ignore declare variables in definition files shadowing global variables (#​10710)
• eslint-plugin: [no-restricted-imports] support regex option (#​10699)
• eslint-plugin: [dot-notation] handle noPropertyAccessFromIndexSignature true (#​10644)
• eslint-plugin: [prefer-nullish-coalescing] fix missing return (#​10732)
• bump ts-api-utils to ^2.0.1 (#​10761)
• eslint-plugin: [no-unnecessary-template-expression] allow interpolating type parameter in type context (#​10739)
• eslint-plugin: [switch-exhaustiveness-check] suggest with qualified name (#​10697)
• eslint-plugin: [no-unnecessary-type-assertion] should report readonly class properties with a literal initializer (#​10618)

❤️ Thank You

• Josh Goldberg ✨
• Olivier Zalmanski @​OlivierZal
• Ryan Poon @​sopa301
• YeonJuan @​yeonjuan
• Yukihiro Hasegawa @​y-hsgw

You can read about our versioning strategy and releases on our website.

v8.22.0

Compare Source

🩹 Fixes

• eslint-plugin: [no-unnecessary-template-expression] handle template literal type (#​10612)
• eslint-plugin: [prefer-readonly] autofixer doesn't add type to property that is mutated in the constructor (#​10552)
• eslint-plugin: [no-extraneous-class] handle accessor keyword (#​10678)
• eslint-plugin: [no-shadow] don't report unnecessarily on valid ways of using module augmentation (#​10616)
• eslint-plugin: [no-duplicate-type-constituents] handle nested types (#​10638)
• eslint-plugin: [prefer-nullish-coalescing] doesn't report on ternary but on equivalent || (#​10517)

❤️ Thank You

• mdm317
• Olivier Zalmanski @​OlivierZal
• Ronen Amiel
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

v8.26.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.26.0

Compare Source

🚀 Features

• support TypeScript 5.8 (#​10903)

❤️ Thank You

• Dirk Luijk @​dirkluijk

You can read about our versioning strategy and releases on our website.

v8.25.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.24.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.24.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.23.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.22.0

Compare Source

🚀 Features

• parser: add standalone isolatedDeclarations option (#​10499)

❤️ Thank You

• Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

v4.2.0

Compare Source

What's Changed

• Enhance workflows and upgrade publish-actions from 0.2.2 to 0.3.0 by @​aparnajyothi-y in https://github.com/actions/setup-node/pull/1174
• Add recommended permissions section to readme by @​benwells in https://github.com/actions/setup-node/pull/1193
• Configure Dependabot settings by @​HarithaVattikuti in https://github.com/actions/setup-node/pull/1192
• Upgrade @actions/cache to ^4.0.0 by @​priyagupta108 in https://github.com/actions/setup-node/pull/1191
• Upgrade pnpm/action-setup from 2 to 4 by @​dependabot in https://github.com/actions/setup-node/pull/1194
• Upgrade actions/publish-immutable-action from 0.0.3 to 0.0.4 by @​dependabot in https://github.com/actions/setup-node/pull/1195
• Upgrade semver from 7.6.0 to 7.6.3 by @​dependabot in https://github.com/actions/setup-node/pull/1196
• Upgrade @​types/jest from 29.5.12 to 29.5.14 by @​dependabot in https://github.com/actions/setup-node/pull/1201
• Upgrade undici from 5.28.4 to 5.28.5 by @​dependabot in https://github.com/actions/setup-node/pull/1205

New Contributors

• @​benwells made their first contribution in https://github.com/actions/setup-node/pull/1193

Full Changelog: actions/setup-node@v4...v4.2.0

v0.25.1

Compare Source

• Fix incorrect paths in inline source maps (#​4070, #​4075, #​4105)

  This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline sourceMappingURL data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing the sourceMappingURL comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.

• Fix invalid generated source maps (#​4080, #​4082, #​4104, #​4107)

  This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.

  This fix was contributed by @​jridgewell.

• Fix a regression with non-file source map paths (#​4078)

  The format of paths in source maps that aren't in the file namespace was unintentionally changed in version 0.25.0. Path namespaces is an esbuild-specific concept that is optionally available for plugins to use to distinguish paths from file paths and from paths meant for other plugins. Previously the namespace was prepended to the path joined with a : character, but version 0.25.0 unintentionally failed to prepend the namespace. The previous behavior has been restored.

• Fix a crash with switch optimization (#​4088)

  The new code in the previous release to optimize dead code in switch statements accidentally introduced a crash in the edge case where one or more switch case values include a function expression. This is because esbuild now visits the case values first to determine whether any cases are dead code, and then visits the case bodies once the dead code status is known. That triggered some internal asserts that guard against traversing the AST in an unexpected order. This crash has been fixed by changing esbuild to expect the new traversal ordering. Here's an example of affected code:

  switch (x) {
    case '':
      return y.map(z => z.value)
    case y.map(z => z.key).join(','):
      return []
  }

• Update Go from 1.23.5 to 1.23.7 (#​4076, #​4077)

  This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.

  This PR was contributed by @​MikeWillCook.

v0.25.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.24.0 or ~0.24.0. See npm's documentation about semver for more information.

• Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

  This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

  Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

  In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

  Thanks to @​sapphi-red for reporting this issue.

• Delete output files when a build fails in watch mode (#​3643)

  It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

• Fix correctness issues with the CSS nesting transform (#​3620, #​3877, #​3933, #​3997, #​4005, #​4037, #​4038)

  This release fixes the following problems:

  • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using :is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

    /* Original code */
    .parent {
      > .a,
      > .b1 > .b2 {
        color: red;
      }
    }
    
    /* Old output (with --supported:nesting=false) */
    .parent > :is(.a, .b1 > .b2) {
      color: red;
    }
    
    /* New output (with --supported:nesting=false) */
    .parent > .a,
    .parent > .b1 > .b2 {
      color: red;
    }

    Thanks to @​tim-we for working on a fix.

  • The & CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered && to have the same specificity as &. With this release, this should now work correctly:

    /* Original code (color should be red) */
    div {
      && { color: red }
      & { color: blue }
    }
    
    /* Old output (with --supported:nesting=false) */
    div {
      color: red;
    }
    div {
      color: blue;
    }
    
    /* New output (with --supported:nesting=false) */
    div:is(div) {
      color: red;
    }
    div {
      color: blue;
    }

    Thanks to @​CPunisher for working on a fix.

  • Previously transforming nested CSS incorrectly removed leading combinators from within pseudoclass selectors such as :where(). This edge case has been fixed and how has test coverage.

    /* Original code */
    a b:has(> span) {
      a & {
        color: green;
      }
    }
    
    /* Old output (with --supported:nesting=false) */
    a :is(a b:has(span)) {
      color: green;
    }
    
    /* New output (with --supported:nesting=false) */
    a :is(a b:has(> span)) {
      color: green;
    }

    This fix was contributed by @​NoremacNergfol.

  • The CSS minifier contains logic to remove the & selector when it can be implied, which happens when there is only one and it's the leading token. However, this logic was incorrectly also applied to selector lists inside of pseudo-class selectors such as :where(). With this release, the minifier will now avoid applying this logic in this edge case:

    /* Original code */
    .a {
      & .b { color: red }
      :where(& .b) { color: blue }
    }
    
    /* Old output (with --minify) */
    .a{.b{color:red}:where(.b){color:#​00f}}
    
    /* New output (with --minify) */
    .a{.b{color:red}:where(& .b){color:#​00f}}

• Fix some correctness issues with source maps (#​1745, #​3183, #​3613, #​3982)

  Previously esbuild incorrectly treated source map path references as file paths instead of as URLs. With this release, esbuild will now treat source map path references as URLs. This fixes the following problems with source maps:

  • File names in sourceMappingURL that contained a space previously did not encode the space as %20, which resulted in JavaScript tools (including esbuild) failing to read that path back in when consuming the generated output file. This should now be fixed.

  • Absolute URLs in sourceMappingURL that use the file:// scheme previously attempted to read from a folder called file:. These URLs should now be recognized and parsed correctly.

  • Entries in the sources array in the source map are now treated as URLs instead of file paths. The correct behavior for this is much more clear now that source maps has a formal specification. Many thanks to those who worked on the specification.

• Fix incorrect package for @esbuild/netbsd-arm64 (#​4018)

  Due to a copy+paste typo, the binary published to @esbuild/netbsd-arm64 was not actually for arm64, and didn't run in that environment. This release should fix running esbuild in that environment (NetBSD on 64-bit ARM). Sorry about the mistake.

• Fix a minification bug with bitwise operators and bigints (#​4065)

  This change removes an incorrect assumption in esbuild that all bitwise operators result in a numeric integer. That assumption was correct up until the introduction of bigints in ES2020, but is no longer correct because almost all bitwise operators now operate on both numbers and bigints. Here's an example of the incorrect minification:

  // Original code
  if ((a & b) !== 0) found = true
  
  // Old output (with --minify)
  a&b&&(found=!0);
  
  // New output (with --minify)
  (a&b)!==0&&(found=!0);

• Fix esbuild incorrectly rejecting valid TypeScript edge case (#​4027)

  The following TypeScript code is valid:

  export function open(async?: boolean): void {
    console.log(async as boolean)
  }

  Before this version, esbuild would fail to parse this with a syntax error as it expected the token sequence async as ... to be the start of an async arrow function expression async as => .... This edge case should be parsed correctly by esbuild starting with this release.

• Transform BigInt values into constructor calls when unsupported (#​4049)

  Previously esbuild would refuse to compile the BigInt literals (such as 123n) if they are unsupported in the configured target environment (such as with --target=es6). The rationale was that they cannot be polyfilled effectively because they change the behavior of JavaScript's arithmetic operators and JavaScript doesn't have operator overloading.

  However, this prevents using esbuild with certain libraries that would otherwise work if BigInt literals were ignored, such as with old versions of the buffer library before the library fixed support for running in environments without BigInt support. So with this release, esbuild will now turn BigInt literals into BigInt constructor calls (so 123n becomes BigInt(123)) and generate a warning in this case. You can turn off the warning with --log-override:bigint=silent or restore the warning to an error with --log-override:bigint=error if needed.

• Change how console API dropping works (#​4020)

  Previously the --drop:console feature replaced all method calls off of the console global with undefined regardless of how long the property access chain was (so it applied to console.log() and console.log.call(console) and console.log.not.a.method()). However, it was pointed out that this breaks uses of console.log.bind(console). That's also incompatible with Terser's implementation of the feature, which is where this feature originally came from (it does support bind). So with this release, using this feature with esbuild will now only replace one level of method call (unless extended by call or apply) and will replace the method being called with an empty function in complex cases:

  // Original code
  const x = console.log('x')
  const y = console.log.call(console, 'y')
  const z = co